Marker Handling in Markdown++ Output

Markers in Markdown++ provide metadata and processing instructions that can be embedded in your output documents. ePublisher gives you control over which markers are emitted in the generated Markdown++ output.

Built-in Markers

Built-in markers are emitted automatically in the Markdown++ output without requiring configuration in the Stationery. These markers capture important metadata from your source documents.

PageStyle

Specifies page layout information from the source document.

GraphicStyle

Specifies graphic formatting information from the source document.

IndexMarker

Creates index entries that can be used for generating back-of-book style indexes.

Controlling Marker Emission

By default, markers are emitted in the Markdown++ output. To prevent markers from being emitted, configure paragraph style options using the Style Designer.

Disabling Markers for All Content

To disable markers globally, modify the [Prototype] paragraph style (the default style). In the Style Designer, select the Options tab and set the Markdown++ markers option to Disabled. All paragraph styles inherit from this default.

Disabling Markers Per Style

To control marker emission on a style-by-style basis, select the specific paragraph style in the Style Designer. On the Options tab, set the Markdown++ markers option to Disabled for styles that should not emit markers.

Marker Syntax in Markdown++ Output

Markers in Markdown++ output use the comment-based marker syntax:

<!-- marker:PageStyle="FirstPage" -->

<!-- marker:IndexMarker="creating projects" -->

For multiple marker entries, use the JSON format:

<!-- markers:{"IndexMarker": "projects:creating,output:generating"} -->

Special Characters in Marker Values

ePublisher writes a marker in the marker:Name="value" form only when the result reads back exactly. That requires a name made of letters, digits, _, and -, with no spaces, and a value with no quotation mark ("), backslash, ;, |, line break, -->, or leading or trailing spaces. Any other marker is written in the markers: form, with its name and value escaped as JSON:

  • \" is a quotation mark, \` a backslash, and \n, \r, and \t` are a line feed, a carriage return, and a tab.

  • \u003b is a ;, \u007c is a |, and \u003e is the > of a --> in the value.

  • Other control characters are written as \u00 followed by two hexadecimal digits.

<!-- markers:{"Description":"Covers the \"Quick Start\" steps"} -->

A marker name that contains a space or starts with an underscore is always written in the markers: form, which every version of ePublisher reads. A plain HTML comment directly above a paragraph in the source comes back as a PassThrough marker that holds the comment:

<!-- markers:{"PassThrough":"<!-- TODO --\u003e\n"} -->

Markers on Inline Text

A marker on a run of bold, italic, strikethrough, or code text, or on a link, is written inline, directly in front of that text, so it reads back on the same text:

Run <!-- marker:Keywords="setup" -->**Setup.exe** to start.

Markers on the paragraph itself, and on inline content without its own syntax, such as an image, are written in the comment tag above the paragraph. The Markdown++ markers option of the paragraph's style controls both.

Last modified date: 2026-10-02